<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html dir="ltr" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en"><head>


<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="KEYWORDS" content="Talk:Flex Ant Tasks">
<meta name="robots" content="index,follow">
<link rel="shortcut icon" href="http://labs.adobe.com/favicon.ico">
<title>
Talk:Flex Ant Tasks - Adobe Labs</title>
<meta http-equiv="imagetoolbar" content="no">
<script type="text/javascript" src="Talk%20Flex_Ant_Tasks_files/index.php"></script>
<script type="text/javascript" src="Talk%20Flex_Ant_Tasks_files/wikibits.js"></script>
<link rel="stylesheet" type="text/css" href="Talk%20Flex_Ant_Tasks_files/labs_wiki_import.css">
<script type="text/javascript" src="Talk%20Flex_Ant_Tasks_files/omtr_tc.js"></script></head><div FirebugVersion="1.3.3" style="display: none;" id="_firebugConsole"></div><body class="ns-1">

<a id="p-logo" href="http://labs.adobe.com/" title="Main Page"></a>

<div id="pod">
  <h5>
    <label for="searchInput">
    Search    </label>
  </h5>
  <form name="searchform" action="/wiki/index.php/Special:Search" id="searchform">
    <input id="searchInput" name="search" accesskey="f" value="" type="text">
    <input name="go" class="searchButton submit" id="searchGoButton" value="Go" type="submit">

    &nbsp;
    <input name="fulltext" class="searchButton submit" value="Search" type="submit">
  </form>
  <ul class="nav-pod">
    <li>
      <p>Navigation</p>
      <ul>
        <li id="n-labshome"><a href="http://labs.adobe.com/">Labs Home</a></li>
        <li id="n-mainpage"><a href="http://labs.adobe.com/wiki/index.php/Main_Page">Wiki Home</a></li>
      </ul>
    </li>
    <li>
      <p>Technologies</p>
      <ul>
    <li><a href="http://labs.adobe.com/wiki/index.php/AIR_for_Linux">Adobe AIR for Linux</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Adobe_AIR_Update_Framework">Adobe AIR Update Framework</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Alchemy">Alchemy</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Bolt">Bolt</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/DNG_Profiles">Camera Profiles and DNG Profile Editor</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Centaur">Centaur</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/ColdFusion_Portlet_Toolkit">ColdFusion Portlet Toolkit</a></li>
	<li><a href="http://labs.adobe.com/wiki/index.php/Data_Services_Stress_Testing_Framework">Data Services Stress Testing Framework</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Dreamweaver_Widget_Packager">Dreamweaver Widget Packager</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/DNG_Codec">DNG Codec</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Flash_Lite_for_BREW_Publisher_for_Flash_CS3_Pro">Flash Lite for BREW Publisher for Flash CS3 Professional</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Flash-Ajax_Video_Component">Flash-Ajax Video Component</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Genesis">Genesis</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Gumbo">Gumbo</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/InContext_Editing">InContext Editing</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/InDesign_Plug-in_Editor">InDesign Plug-in Editor</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Knowhow">knowhow</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Mars">Mars</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/NoteTag">NoteTag</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/PatchPanel">PatchPanel</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Camera_Raw_5.4">Photoshop Camera Raw 5.4</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Photoshop_CS3_Extended_Plug-In_for_Google_3D_Warehouse">Photoshop CS3 Extended Plug-In for Google 3D Warehouse</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Pixmantec_RawShooter_Migration_Tool">Pixmantec RawShooter Migration Tool</a></li>
	<li><a href="http://labs.adobe.com/wiki/index.php/Adobe_Premiere_Pro_Update_for_Intel_SSE4.1">Adobe Premiere Pro Update for Intel SSE4.1</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Spry">Spry framework for Ajax</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Story">Story</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Stratus">Stratus</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/SwitchBoard">SwitchBoard</a></li>
    <li><a href="http://labs.adobe.com/wiki/index.php/Adobe_Wave">Adobe Wave</a></li>
      </ul>
    </li>
    <li><p><a href="http://labs.adobe.com/wiki/index.php/Showcase">Showcase Gallery</a></p></li>
    <li><p><a href="http://labs.adobe.com/wiki/index.php/Special:Recentchanges">Recent Changes</a></p></li>
    <li><p><a href="http://labs.adobe.com/wiki/index.php?title=Special:Recentchanges&amp;feed=rss">Recent Changes (RSS)</a></p></li>
    <li><p><a href="http://labs.adobe.com/wiki/index.php/Help:Contents">Help</a></p></li>
    <li><p><a href="http://labs.adobe.com/wiki/index.php/FAQ">FAQ</a></p></li>
    <li>
      <p>Toolbox</p>
      <ul>
        <li><a href="http://labs.adobe.com/wiki/index.php?title=Special:Whatlinkshere&amp;target=Talk:Flex_Ant_Tasks">What Links Here</a></li>
        <li><a href="http://labs.adobe.com/wiki/index.php?title=Special:Recentchangeslinked&amp;target=Talk:Flex_Ant_Tasks">Related Changes</a></li>
        <li><a href="http://labs.adobe.com/wiki/index.php/Special:Specialpages">Special Pages</a></li>
      </ul>
    </li>
  </ul>

</div>
<div id="p-personal">
  <h5>
    Personal tools  </h5>
  <ul>
        <li id="pt-login"><a href="http://labs.adobe.com/wiki/index.php?title=Special:Userlogin&amp;returnto=Talk:Flex_Ant_Tasks">
      Create an account or log in      </a></li>

      </ul>
</div>
<br class="clear-both">
<div id="p-cactions">
  <h5>Views</h5>
  <ul>
        <li id="ca-nstab-main">

	         <a href="http://labs.adobe.com/wiki/index.php/Flex_Ant_Tasks">
      Article      </a></li>
        <li id="ca-talk" class="selected">

	         <a href="http://labs.adobe.com/wiki/index.php/Talk:Flex_Ant_Tasks">
      Discussion      </a></li>
        <li id="ca-edit" class="istalk">

	         <a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit">
      Edit      </a></li>
        <li id="ca-addsection">

	         <a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=new">
      +      </a></li>
        <li id="ca-history">

	         <a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=history">
      History      </a></li>
      </ul>
</div>
<div id="content"> <a name="top" id="contentTop"></a>
    <h1 class="firstHeading">
    Talk:Flex Ant Tasks  </h1>
  <h3 id="siteSub">
    From Adobe Labs  </h3>
  <div id="contentSub">

      </div>
      <!-- start content -->
  <table class="tochidden" id="toc" border="0"><tbody><tr id="toctitle"><td align="center">
<b>Table of contents</b> <script type="text/javascript">showTocToggle("show","hide")</script><span class="toctoggle">[<a href="javascript:toggleToc()" class="internal"><span id="showlink" style="">show</span><span style="display: none;" id="hidelink">hide</span></a>]</span>
</td></tr><tr style="display: none;" id="tocinside"><td>
<div class="tocline"><a href="#Welcome.21">1 Welcome!</a><br></div>
<div class="tocindent">
<p><a href="#Official_documentation.">1.1 Official documentation.</a><br>
</p>
</div>
<div class="tocline"><a href="#Question:_Ant_Version">2 Question: Ant Version</a><br></div>
<div class="tocindent">
<p><a href="#Version_1.6.2">2.1 Version 1.6.2</a><br>
</p>
</div>
<div class="tocline"><a href="#Ant_Task_fix_for_Mac_OS_X">3 Ant Task fix for Mac OS X</a><br></div>
<div class="tocindent">
<p><a href="#FLEX_HOME">3.1 FLEX_HOME</a><br>
</p>
</div>
<div class="tocline"><a href="#Tasks_don.27t_support_spaces_in_paths">4 Tasks don't support spaces in paths</a><br></div>
<div class="tocindent">
<p><a href="#Try_using_a_symbol">4.1 Try using a symbol</a><br>
<a href="#Spaces_and_quoting">4.2 Spaces and quoting</a><br>
</p>
</div>
<div class="tocline"><a href="#Inconsistent_taskdef_explanation">5 Inconsistent taskdef explanation</a><br></div>
<div class="tocline"><a href="#Ant_version_requirements">6 Ant version requirements</a><br></div>
<div class="tocline"><a href="#FLEX_HOME_MUST_be_set">7 FLEX_HOME MUST be set</a><br></div>
<div class="tocline"><a href="#ant_task_for_asdoc.3F">8 ant task for asdoc?</a><br></div>
<div class="tocline"><a href="#Bug_Fixes.3F_Here.27s_one.">9 Bug Fixes? Here's one.</a><br></div>
<div class="tocindent">
<p><a href="#HtmlWrapperTask.27s_resources">9.1 HtmlWrapperTask's resources</a><br>
</p>
</div>
<div class="tocline"><a href="#mxmlc_task_does_not_fail_on_error">10 mxmlc task does not fail on error</a><br></div>
<div class="tocline"><a href="#mxmlc_task_does_not_fail_on_error_.282.29">11 mxmlc task does not fail on error (2)</a><br></div>
<div class="tocline"><a href="#Maven_support">12 Maven support</a><br></div>
<div class="tocline"><a href="#Next_release_schedule.3F">13 Next release schedule?</a><br></div>
<div class="tocline"><a href="#Compc_Task">14 Compc Task</a><br></div>
<div class="tocline"><a href="#include-classes_without_pattern_matching">15 include-classes without pattern matching</a><br></div>
<div class="tocline"><a href="#Tasks_without_exec">16 Tasks without exec</a><br></div>
<div class="tocline"><a href="#Step_by_Step_for_Newbies">17 Step by Step for Newbies</a><br></div>
<div class="tocindent">
<p><a href="#Eclipse_configuration">17.1 Eclipse configuration</a><br>
</p>
</div>
<div class="tocline"><a href="#history.swf_not_loaded">18 history.swf not loaded</a><br></div>
<div class="tocline"><a href="#Bug_in_html-wrapper_task">19 Bug in html-wrapper task</a><br></div>
<div class="tocline"><a href="#How_to_use_.27include-namespaces.27_with_compc_task.3F">20 How to use 'include-namespaces' with compc task?</a><br></div>
<div class="tocline"><a href="#Flex_Ant_Tasks_for_Apollo">21 Flex Ant Tasks for Apollo</a><br></div>
<div class="tocline"><a href="#How_to_Compile_multiple_.mxml">22 How to Compile multiple .mxml</a><br></div>
<div class="tocline"><a href="#Loading_flex-config_takes_ages">23 Loading flex-config takes ages</a><br></div>
<div class="tocline"><a href="#Custom_wrapper_task_template.3F">24 Custom wrapper task template?</a><br></div>
<div class="tocline"><a href="#Minor_mod_to_html-wrapper_task_offered">25 Minor mod to html-wrapper task offered</a><br></div>
<div class="tocline"><a href="#Adding_to_default_loaded_flex-config.xml">26 Adding to default loaded flex-config.xml</a><br></div>
<div class="tocline"><a href="#Flex_3_support.3F.3F">27 Flex 3 support??</a><br></div>
<div class="tocindent">
<p><a href="#Try_the_flexTasks.jar_that_ships_with_the_v3_sdk">27.1 Try the flexTasks.jar that ships with the v3 sdk</a><br>
</p>
</div>
<div class="tocline"><a href="#Ant_Build_Errors_Integrated_into_Eclipse">28 Ant Build Errors Integrated into Eclipse</a><br></div>
<div class="tocline"><a href="#Attributes_for_runtime-shared-library-path">29 Attributes for runtime-shared-library-path</a><br></div>
<div class="tocline"><a href="#Problem_with_compc_task_on_linux_.28.27unknown_configuration_variable_compiler.source-path.27.29">30 Problem with compc task on linux ('unknown configuration variable compiler.source-path')</a><br></div>
<div class="tocline"><a href="#dynamically_adding_assets_to_compc">31 dynamically adding assets to compc</a><br></div>
<div class="tocline"><a href="#flex-config.xml_error">32 flex-config.xml error</a><br></div>
<div class="tocline"><a href="#compc_compiling_assets_from_custom_task">33 compc compiling assets from custom task</a><br></div>
</td></tr></tbody></table>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=1" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Welcome.21"></a><h2> Welcome! </h2>
<p>Welcome to the Flex Ant Tasks discussion page on Adobe Labs. Please
enter your comments regarding this technology here. To help identify
the author of comments, please create a new section and use ~~~~ at the
end of your talk entries to automatically create a signature.
</p><p>Comments should be added in list format, but feel free to add
your comment under an existing comment to follow a thread structure. If
you are responding to a thread, please use the H3 style for your
subject (=== TEXT ===) so that the page is easier to read.
</p><p><a href="http://labs.adobe.com/wiki/index.php/User:Daniel_T" title="User:Daniel T">Daniel T</a> 12:30, 24 Jan 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=2" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Official_documentation."></a><h3> Official documentation. </h3>
<p>Flex 3 docs are here: <a href="http://livedocs.adobe.com/flex/3/html/help.html?content=anttasks_1.html" class="external" rel="nofollow" target="_blank">http://livedocs.adobe.com/flex/3/html/help.html?content=anttasks_1.html</a>
</p><p>This page references out of date Adobe products, but may be
useful for historic purposes. It is a top web search hit for "Flex ant
tasks". When flex 4 becomes available, add another link to this comment
please.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:Mchenryc&amp;action=edit" class="new" title="User:Mchenryc">mchenryc</a> 09:45, 25 Feb 2009 (PST)
</p>
<hr>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=3" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Question:_Ant_Version"></a><h2> Question: Ant Version </h2>
<p>What version of ant is needed to use this?  Is the task compatible with ant 1.6.x or is the new 1.7 version needed?
</p><p>Thanks,
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Rkinion&amp;action=edit" class="new" title="User:Rkinion">rkinion</a> 12:09, 25 Jan 2007 (PST)
</p><p><br>
I'd also like to know the Ant version required...
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Markmontymark&amp;action=edit" class="new" title="User:Markmontymark">markmontymark</a> 12:09, 25 Jan 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=4" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Version_1.6.2"></a><h3> Version 1.6.2 </h3>
<p>The ant tasks might work with earlier versions, but we developed the Ant tasks using 1.6.2.
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Paul_Reilly&amp;action=edit" class="new" title="User:Paul Reilly">Paul Reilly</a> 07:39, 7 Feb 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=5" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Ant_Task_fix_for_Mac_OS_X"></a><h2> Ant Task fix for Mac OS X </h2>
<p>Under Mac OS X 10.4.8, when I first tried the Ant build example I got the error:
</p><p><b>"Command not found: mxmlc"</b>
</p><p>Searching the Internet I found a solution to the problem on a Japanese website ( [<a href="http://d.hatena.ne.jp/flashrod/20070127" class="external" title="http://d.hatena.ne.jp/flashrod/20070127" rel="nofollow" target="_blank">[1]</a>]) using Google Translation ([<a href="http://translate.google.com/translate?u=http%3A%2F%2Fd.hatena.ne.jp%2Fflashrod%2F20070127&amp;langpair=ja%7Cen&amp;hl=en&amp;safe=off&amp;ie=UTF-8&amp;oe=UTF-8&amp;prev=%2Flanguage_tools" class="external" title="http://translate.google.com/translate?u=http://d.hatena.ne.jp/flashrod/20070127&amp;langpair=ja|en&amp;hl=en&amp;safe=off&amp;ie=UTF-8&amp;oe=UTF-8&amp;prev=/language tools" rel="nofollow" target="_blank">[2]</a>])
I was able to decipher that to fix the problem you have to set
environmental variables for Ant for the Flex SDK and Java home (if a
unix guru out there knows why this is necessary please let me know!).
Anyway I typed the following into terminal (<b>NOTE: DO NOT TYPE THE "$" AND "&gt;" SYMBOLS, THEY ARE SIMPLY TO SHOW WHEN YOU ARE IN THE SHELL AND WHEN YOU ARE IN PICO</b>):
</p><p>$ cd
</p><p>$ pico .antrc
</p><p>&gt; JAVA_HOME=/Library/Java/Home
</p><p>&gt; export JAVA_HOME
</p><p>&gt; PATH=/Developer/SDKs/Flex2.sdk/bin:$PATH
</p><p>&gt; export PATH
</p><p>[press 'Control-x']
</p><p>[press 'y']
</p><p>[hit return]
</p><p>Of course, change the Flex SDK path, to the path to the SDK on your machine.
Now the ant example should work.
</p><p>Cheers!
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Ans&amp;action=edit" class="new" title="User:Ans">Ans</a> 20:03, 28 Jan 2007 (PST)
</p><p>I'm having the same issue on XP. Tried this fix there, with no luck. Does anyone else have the mxmlc target working on XP?
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:Goorange44&amp;action=edit" class="new" title="User:Goorange44">goorange44</a> 13:15, 30 Jan 2007 (PST)
</p><p>I'm also having the same issue with XP Pro, not sure what else to check.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:SalmonArm&amp;action=edit" class="new" title="User:SalmonArm">SalmonArm</a> 14:42, 31 Jan 2007 (PST)
</p><p>Same problem on Gentoo Linux here. As the poster below says, the FLEX_HOME must be set:
</p>
<pre>    &lt;property name="FLEX_HOME" value="/opt/flex2"/&gt;
</pre>
<p>The above property declaration works in Win XP Pro as well when receiving the 
<i>command not found: mxmlc" failture.</i>
</p>
<pre>   &lt;property name="FLEX_HOME" value="C:\dev\flex_sdk_2"/&gt;
</pre>
<p>Also, I made the mistake building flexTasks.jar using the ant build script. The resulting flexTask.jar didn't work.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=6" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="FLEX_HOME"></a><h3> FLEX_HOME </h3>
<p>Yah, the FLEX_HOME property isn't designed to be optional. I use the
Ant tasks on Windows XP and Fedora Core 5. When I set FLEX_HOME, it
works great on both OS's.
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Paul_Reilly&amp;action=edit" class="new" title="User:Paul Reilly">Paul Reilly</a> 07:47, 7 Feb 2007 (PST)
</p><p>I wouldn't recommend putting FLEX_HOME in each ant build file.
If it ever changes you have to edit all your projects to get things
working again. Kinda like storing the MS Word installation path in each
Word file. A second reason is that it breaks cross-platform use. If one
developer uses OS-X and the other Linux then the FLEX_HOME paths will
differ.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:SalmonArm&amp;action=edit" class="new" title="User:SalmonArm">SalmonArm</a> 22:48, 3 Dec 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=7" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Tasks_don.27t_support_spaces_in_paths"></a><h2> Tasks don't support spaces in paths </h2>
<p>My test project had a space in it's parent directory's name, which made mxmlc spit out the error message:
</p><p>[mxmlc] command line: Error: default arguments may not be interspersed with other options
</p><p>[mxmlc] Use 'mxmlc -help' for information about using the command line.
</p><p>Not very useful...
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=8" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Try_using_a_symbol"></a><h3> Try using a symbol </h3>
<p>Define your path as an ant symbol and use the symbol in the
argument. Might work. (For windows paths, sometimes it seems I need to
make the symbol a property in an external .properties file. I probably
just don't know the right escape sequences/special chars/whatever...)
--<a href="http://labs.adobe.com/wiki/index.php?title=User:Cluebcke&amp;action=edit" class="new" title="User:Cluebcke">cluebcke</a> 16:15, 30 Jan 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=9" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Spaces_and_quoting"></a><h3> Spaces and quoting </h3>
<p>I don't think using a symbol is going to help. I suspect the problem
isn't with how Ant is processing the arguments, but with how they are
being passed to mxmlc. Using mxmlc from the command line with string
arguments including spaces requires some quoting trickery. The quoting
requirements also vary from Windows to Mac to Linux. We tried hard to
make everything that works via the command line also work from the Ant
tasks, but I'm sure we missed some edge cases. The good news is that we
included the source code, so you can hack up fixes for the cases we
missed. Please report fixes back to us, so we can include them in
future updates. Thanks.
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Paul_Reilly&amp;action=edit" class="new" title="User:Paul Reilly">Paul Reilly</a> 07:58, 7 Feb 2007 (PST)
</p><p>I am having the same issue. Default path of Flex SDK on MAC has spaces in it 
</p><p>/Applications/Adobe b Flex b Builder b 2 b Plug-in/Flex b SDK b 2/
</p><p>I tried putting backslash (\) as escape sequence, didnt work
</p><p>/Applications/Adobe\ Flex\ Builder\ 2\ Plug-in/Flex\ SDK\ 2/
</p><p>Anyone solved this issue?
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:David_tudury&amp;action=edit" class="new" title="User:David tudury">david tudury</a> 08:11, 24 Aug 2007 (PDT)
</p><p>maybe make a symbolic link like:
</p><p>ln -s /Applications/Adobe\ Flex\ Builder\ 3/sdks/2.0.1/ /usr/share/flex2
</p><p>then use the path /usr/share/flex2 instead
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:ArronH&amp;action=edit" class="new" title="User:ArronH">ArronH</a>
15:03, 21 Nov 2007 (PST)
I've found that I can work around this on Windows by surrounding
filenames and paths with double quotes. If I'm calling the java
compiler, I can do something like this below where any filenames with
spaces are surrounded by quotes:
</p>
<pre>...

&lt;pathconvert property="compc2.lib.files" refid="@{lib.path.id}" pathsep=","&gt;
	&lt;mapper type="regexp" from="^(.*)(\s)*(.*)$$" to='"\1\2\3"'/&gt;
&lt;/pathconvert&gt;
&lt;condition property="compc2.libpath" value="-library-path+=${compc2.lib.files}" else=""&gt;
	&lt;not&gt;
		&lt;equals arg1="" arg2="${compc2.lib.files}" trim="true" /&gt;
	&lt;/not&gt;
&lt;/condition&gt;
&lt;java jar="${flex.compc.jar}" dir="." fork="true" failonerror="true"&gt;
	&lt;jvmarg value="-Xmx512m" /&gt;
	&lt;arg line="@{options} ${compc2.libpath}" /&gt;
	&lt;arg value="+flexlib=${flex.frameworks.dir}" /&gt;
	&lt;arg value="-load-config=@{config}" /&gt;
	&lt;arg value="-source-path=@{src.dir}" /&gt;
	&lt;arg value="-include-sources=@{src.dir}" /&gt;
	&lt;arg value="-output=@{dest}" /&gt;
&lt;/java&gt;
</pre>
<p>The combination of the <code>&lt;arg line="..."/&gt;</code> and the double quotes allows the argument to get to the flex compiler correctly.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=10" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Inconsistent_taskdef_explanation"></a><h2> Inconsistent taskdef explanation </h2>
<p>The docs says that you should install flexTasks.jar in Ant's
lib-directory, and then continues with an example that says to include
the path to the jar as classpath into the project's lib directory. The
example code then puts in the projects flexTask/lib directory. Quite
confusing.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:SalmonArm&amp;action=edit" class="new" title="User:SalmonArm">SalmonArm</a> 15:33, 31 Jan 2007 (PST)
</p><p>I found that both will work, so you have a choice of either solution. No need to do both.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=11" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Ant_version_requirements"></a><h2> Ant version requirements </h2>
<p>rkinion, markmontymark: We use ant 1.6.2, but newer versions of ant should work.
</p><p>hth,
</p><p>matt horn
flex docs
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Danger42&amp;action=edit" class="new" title="User:Danger42">danger42</a> 07:40, 30 Jan 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=12" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="FLEX_HOME_MUST_be_set"></a><h2> FLEX_HOME <i>MUST</i> be set </h2>
<p>Best guess is that there's a hardcoded reference in the mxmlc task
to FLEX_HOME, rather than relying on a fully-parameterized input. Since
I already had an exec-style mxmlc task, I already had an sdk home
defined and so didn't think I needed to do it again. I finally found
that adding FLEX_HOME--<i>although it's not referenced anywhere in my build.xml file</i>--made the "command not found" problem vanish.
</p><p>Now on to make the rest of it work...
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:Cluebcke&amp;action=edit" class="new" title="User:Cluebcke">cluebcke</a> 16:41, 30 Jan 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=13" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="ant_task_for_asdoc.3F"></a><h2> ant task for asdoc? </h2>
<p>I was using forked java tasks to do flex builds with Ant, but real ant tasks are a great improvement. Thanks Adobe!
</p><p>However, I would also like to have an ant task for running ASDoc. My guess is, that that one is already on its way. Am I right?
</p><p>In the meantime, I am using a forked java task to run asdoc:
</p><p>&lt;property name="asdoc" value="flex2.tools.ASDoc" /&gt;
</p><p>&lt;target name="presentation.apidoc"&gt;
</p>
<pre>   &lt;java className="${asdoc}" fork="true" failonerror="true"&gt;
       &lt;classpath&gt;
           &lt;fileset dir="${FLEX_HOME}/asdoc/lib" includes="*.jar" /&gt;
           &lt;fileset dir="${FLEX_HOME}/lib" includes="*.jar" /&gt;
       &lt;/classpath&gt;
       &lt;jvmarg line="-Dapplication.home=${flex.home} -Xms32m -Xmx768m -Dsun.io.useCanonCaches=false -Xbootclasspath/p:${flex.home}/asdoc/lib/xalan.jar"/&gt;
       &lt;arg line="-library-path+=${lib}" /&gt;
       &lt;arg line="-source-path ${basedir}" /&gt;
       &lt;arg line="-doc-sources ${basedir}/${view.main}" /&gt;
       &lt;arg line="-main-title ${apidoc.title}" /&gt;
       &lt;arg line="-window-title ${apidoc.title}" /&gt;
       &lt;arg line="-output ${doc}/${app.name}-API" /&gt;
   &lt;/java&gt;
</pre>
<p>&lt;/target&gt;
</p><p>--<a href="http://labs.adobe.com/wiki/index.php/User:Javamark" title="User:Javamark">javamark</a> 07:13, 5 Feb 2007 (PST)
</p><p>You can use now [<a href="http://www.ericfeminella.com/blog/2007/06/07/asdocanttask-project-for-eclipse/" class="external" rel="nofollow" target="_blank">http://www.ericfeminella.com/blog/2007/06/07/asdocanttask-project-for-eclipse/</a>  from Eric Feminella to generate AntDoc documentation from Ant
--<a href="http://labs.adobe.com/wiki/index.php/User:JabbyPandaUA" title="User:JabbyPandaUA">JabbyPandaUA</a> 15:04, 8 Jun 2007 (GMT+2)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=14" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Bug_Fixes.3F_Here.27s_one."></a><h2> Bug Fixes? Here's one. </h2>
<p>Where can we send bug fixes? FlexTask.java has a bug where only the
first path entry is checked when looking for executables if FLEX_HOME
is not set.
Lines 231 and 232 should be switched so the <code>break</code> is
within
the conditional, or it exits after the first iteration regardless of
outcome. This should fix the reported "Command not found" errors as
well.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:Notalx&amp;action=edit" class="new" title="User:Notalx">notalx</a> 16:18, 5 Feb 2007 (PST)
</p><p>The code that looks for other executables predates the adding of
the FLEX_HOME property. It seems like the proper fix is to remove the
outdated executable hunting and report a build error if FLEX_HOME isn't
set. I'll try to get this into the next update.
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Paul_Reilly&amp;action=edit" class="new" title="User:Paul Reilly">Paul Reilly</a> 08:04, 7 Feb 2007 (PST)
</p><p>I actually quite like not having to set FLEX_HOME. One less step
to getting it all working. Everything else seems to work fine without
it. The executables need to be in the user's PATH for normal usage, so
it seems logical for the ant task to look there as well.
</p><p>At any rate, thanks for the fixes!
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Notalx&amp;action=edit" class="new" title="User:Notalx">notalx</a> 12:28, 7 Feb 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=15" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="HtmlWrapperTask.27s_resources"></a><h3> HtmlWrapperTask's resources </h3>
<p>There's some inconsistencies in where the html templates are
located. In the bundled flexTasks.jar, they are included in
/resources/html-templates/, which matches what build.xml and
HtmlWrapperTask.java expect and where they live in the flex2
distribution. However, in the FlexAntTask download, they are in
resources/. </p><p>This causes problems: they are not included in the jar when
you compile it from the sources, so they are not found unless the flex2
dir is in your classpath. I find it handy to not have to muck with the
classpath, so it seems the simplest and most consistent fix would be to
move the template files from resources/ into resources/html-templates/
in your distro. Probably what you intended in the first place.
</p><p>Thanks for providing the ant tasks.  They're really useful for us command line junkies!
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Notalx&amp;action=edit" class="new" title="User:Notalx">notalx</a>
</p><p>I fixed this a few days ago.  The fix will be included in the next update.  Thanks for reporting it.
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Paul_Reilly&amp;action=edit" class="new" title="User:Paul Reilly">Paul Reilly</a> 08:06, 7 Feb 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=16" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="mxmlc_task_does_not_fail_on_error"></a><h2> mxmlc task does not fail on error </h2>
<p>this is amazing! All mxmlc tasks result in a successfull build.
I have not yet used any of the other flex ant tasks, but the mxmlc task does noet fail on an unsuccessfull compilation.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php/User:Javamark" title="User:Javamark">javamark</a> 13:36, 6 Feb 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=17" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="mxmlc_task_does_not_fail_on_error_.282.29"></a><h2> mxmlc task does not fail on error (2) </h2>
<p>Did I overlook an mxmlc task property (comparable to the failonerror property of the java task)?
</p><p>--<a href="http://labs.adobe.com/wiki/index.php/User:Javamark" title="User:Javamark">javamark</a> 01:15, 7 Feb 2007 (PST)
</p><p>I fixed this a few days ago.  The fix will be in the next update.  Thanks for reporting it.
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Paul_Reilly&amp;action=edit" class="new" title="User:Paul Reilly">Paul Reilly</a> 08:08, 7 Feb 2007 (PST)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=18" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Maven_support"></a><h2> Maven support </h2>
<p>A little offroad question here. Any thoughts about extending support to Maven.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=19" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Next_release_schedule.3F"></a><h2> Next release schedule? </h2>
<p>I was planning to convert my Flex project to use the Flex Ant Tasks
today but, judging from these posts, I should wait until the next
release is made available. Any idea when that will be?
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:TomBaggett&amp;action=edit" class="new" title="User:TomBaggett">TomBaggett</a> 11:17, 13 Feb 2007 (PST)
</p><p><br>
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=20" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Compc_Task"></a><h2> Compc Task </h2>
<p>If you have a large set of class source in a namespace to be
compiled to SWC file, you can use a manifest file to avoid having to
type an all classes&nbsp;?.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=21" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="include-classes_without_pattern_matching"></a><h2> include-classes without pattern matching </h2>
<p>So, what was the rationale behind designing the compc task in such a
way that it is impossible to use any of the benefits of Ant?
</p><p>Without being able to use pattern matching to specify the
classes to include there is no point with the task. Having a separate
config file isn't really an option, since I still would have to
maintain the list by hand.
</p><p>Is there any plans on fixing the compc task? Is it possible to provide code to help you out?
</p><p>A solution purely in Ant, using pathconvert, is <a href="http://snippets.dzone.com/posts/show/3627" class="external" rel="nofollow" target="_blank">http://snippets.dzone.com/posts/show/3627</a>
</p><p>Edit:
sorry, I think I wrote this without thinking it through properly. What
I'm referring to is the include-classes directive of the compc task. To
have to add the classes by hand it the way you have to now is not very
scalable, and I would like to be able to do it with some pattern
matching. However, I now realise that that isn't as easy as I thought,
since it's class names, not paths that are specified. </p><p>I still would like some kind of pattern matching capability in
the include-classes directive, but I guess that is more an issue with
the compc tool than the compc task.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=22" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Tasks_without_exec"></a><h2> Tasks without exec </h2>
<p>Since mxmlc and compc are written in Java, wouldn't it be
appropriate to create a compiler in memory instead of doing the
exec-behind-the-scenes as the tasks do now? That would do away with the
need to set FLEX_HOME (although you would instead have to include that
in the classpath, but that is more natural in Ant). Is it at all
possible to do this? Is the mxml compiler java class designed to be
used only from the command line, or can it be run in-memory as javac
can?
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=23" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Step_by_Step_for_Newbies"></a><h2> Step by Step for Newbies </h2>
<p>I am a newbie to Eclipse and Ant. I know what ANT is but I do not understand the instructions on this page from this point on, <a href="http://labs.adobe.com/wiki/index.php/Flex_Ant_Tasks#Using_Flex_Ant_tasks" class="external" rel="nofollow" target="_blank">http://labs.adobe.com/wiki/index.php/Flex_Ant_Tasks#Using_Flex_Ant_tasks</a>. 
</p><p>For example, here is a few questions that come to mind as I read
the instructions. Quote:
To use the custom Flex Ant tasks in your Ant projects, you must add the
flexTasks.jar file to your project's lib directory (my project doesn't
have a lib directory. what do i do now?), and then point to that JAR
file in the taskdef task (what are you talking about? i've never done
that and don't know how). In addition, for most projects you set the
value of the FLEX_HOME variable so that Ant can find your
flex-config.xml file (don't know why or how to do that?). </p><p>These are just a few questions I had as I read these instructions. I am a newbie. Sue me.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=24" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Eclipse_configuration"></a><h3> Eclipse configuration </h3>
<p>Here's the generalization of what I did:
</p><p>Step 1: Create ant-build Folder in your project
</p>
<ol><li> Right click on your project name and click New.. Folder...
</li><li> For the sake of the example, call the folder "ant-build".
</li><li> Copy the lib folder from Adobe's flex_ant_tasks_mmddyy.zip to
this new folder. The jar file in this lib directory can really go
anywhere on your file system, but this is a good enough place for it
while getting started.
</li></ol>
<p>Step 2: Update Ant Runtime Preferences in Eclipse
</p>
<ol><li> Update the Ant classpath.
<ol><li> Go to Window... Preferences.... Expand the Ant entry on the left and click Runtime.
</li><li> Under the Classpath tab, click Global Entries. Then click Add
External jars and add the flexTasks.jar file in the ant-build/lib
folder created in Step 1.
</li><li> If Eclipse gives you a warning about missing a tools.jar file, refer to this site for guidance: <a href="http://www.dynamicobjects.com/d2r/archives/002591.html" class="external" rel="nofollow" target="_blank">http://www.dynamicobjects.com/d2r/archives/002591.html</a>
</li></ol>
</li><li> Map the Flex Tasks to the correct class. In this step, you
are essentially configuring Eclipse with the mappings from the
flexTasks.tasks file.
<ol><li> Under the Tasks tab, click Add Task...
</li><li> In the name field, enter "mxmlc" (without the quotes).
</li><li> In the location dropdown, select the flexTasks.jar file from Step 1, #3.
</li><li> In the directory tree that appears, select /flex2/ant, and then select MxmlcTask.class.
</li><li> Click OK to add the Flex task.
</li><li> Repeat for "compc" and "html-wrapper", if you plan to use these tasks.
</li></ol>
</li><li> Click OK to apply and exit the Preferences window.
</li></ol>
<p>Step 3: Customizing the build.xml
</p>
<ol><li> Under the "ant-build" folder, create a build.xml file.
</li><li> Copy the sample build file below into this file:
</li><li> Make sure the FLEX_HOME property points to the Flex SDK on
your machine. If you installed the Flex Builder plugin, by default, it
is located in C:\Program Files\Adobe\Flex Builder 2 Plug-in\Flex SDK 2\
</li><li> PROJECT_HOME should point to your Flex project on the file system.
</li><li> MAIN_SOURCE_FOLDER should be the location of your source
files. And OUTPUT_FOLDER should be where the swf files are created when
you run a build. These 2 properties correspond to the entries of the
same name, under the Flex Build Path section of the project properties.
</li></ol>
<p>	<code>
	 &lt;?xml version="1.0" encoding="utf-8"?&gt;
</code></p>
<pre>&lt;project name="My App Builder" basedir="."&gt;
     &lt;property name="FLEX_HOME" value="C:/flex/sdk"/&gt;
    &lt;property name="PROJECT_HOME" value="C:/flex/workspace/MyFlexProject"/&gt;
    &lt;property name="MAIN_SOURCE_FOLDER" value="${PROJECT_HOME}/src"/&gt;  
    &lt;property name="OUTPUT_FOLDER" value="${PROJECT_HOME}/bin"/&gt;  
    &lt;target name="main"&gt;
        &lt;mxmlc file="${MAIN_SOURCE_FOLDER}/Main.mxml" output="${OUTPUT_FOLDER}/Main.swf" keep-generated-actionscript="true"&gt;
            &lt;load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/&gt;
            &lt;source-path path-element="${MAIN_SOURCE_FOLDER"/&gt;
        &lt;/mxmlc&gt;
    &lt;/target&gt;  
&lt;/project&gt;
</pre>
<p>	
</p><p>I hope that helps someone.
</p><p><a href="http://labs.adobe.com/wiki/index.php/User:Ryan_Ma" title="User:Ryan Ma">Ryan Ma</a>
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=25" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="history.swf_not_loaded"></a><h2> history.swf not loaded </h2>
<p>history.swf builded by the html-wrapper task doesn't work.
It has different size with the original .swf from the resouces (2 675 vs 2 656) and does not load.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=26" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Bug_in_html-wrapper_task"></a><h2> Bug in html-wrapper task </h2>
<p>The html-wrapper task does not respect the basedir property of the
ant script. All other ant tasks (including compc and mxmlc) respect
this property, but if you try to call a build script that uses
html-wrapper via the &lt;ant&gt; task or by launching ant from a
different directory, it will generate the index.html file in the
working directory.
</p><p>Does anyone have a workaround for this?
</p>
<hr>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=27" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="How_to_use_.27include-namespaces.27_with_compc_task.3F"></a><h2> How to use 'include-namespaces' with compc task?</h2>
<p>I created the following Ant script: 
</p>
<pre> &lt;target name="compile CustomFlexLibrary SWC"&gt;
   &lt;compc output="${CustomFlexLibraryBin.dir}/CustomFlexLibrary.swc" locale="en_US"&gt;
     &lt;source-path path-element="${CustomFlexLibrarySource.dir}" /&gt;
     &lt;namespace uri="<a href="http://www.company.com/2007/mxml" class="external" rel="nofollow" target="_blank">http://www.company.com/2007/mxml</a>" manifest="${CustomFlexLibrarySource.dir}/customFlexLibrary-manifest.xml" /&gt;
     &lt;include-namespaces uri="<a href="http://www.company.com/2007/mxml" class="external" rel="nofollow" target="_blank">http://www.company.com/2007/mxml</a>" /&gt;
   &lt;/compc&gt;
 &lt;/target&gt;
</pre>
<p>I receive an error in return: 
Error: unknown namespace '<a href="http://www.company.com/2007/mxml%27" class="external" rel="nofollow" target="_blank">http://www.company.com/2007/mxml'</a>
</p><p>Why?
</p>
<hr>
<p><a href="http://labs.adobe.com/wiki/index.php/User:JabbyPandaUA" title="User:JabbyPandaUA">JabbyPandaUA</a> 20:15, 19 Apr 2007 (GMT +2)
</p><p>This worked for me:
</p>
<pre> &lt;target name="compile CustomFlexLibrary SWC"&gt;		
   &lt;compc output="${CustomFlexLibraryBin.dir}/CustomFlexLibrary.swc" locale="en_US" 				
     &lt;source-path path-element="${CustomFlexLibrarySource.dir}"/&gt;
     &lt;namespace uri="<a href="http://www.company.com/2007/mxml" class="external" rel="nofollow" target="_blank">http://www.company.com/2007/mxml</a>" manifest="${CustomFlexLibrarySource.dir}/customFlexLibrary-manifest.xml" /&gt;
     <b>&lt;in uri="<a href="http://www.company.com/2007/mxml" class="external" rel="nofollow" target="_blank">http://www.company.com/2007/mxml</a>"/&gt;	</b>
   &lt;/compc&gt;
 &lt;/target&gt;
</pre>
<p>Yes! the tag is called <i><b>in</b></i> and <b>not include-namespaces</b>. I picked this up from this line in CompcTask.java
private static OptionSpec insSpec = new OptionSpec(null, "include-namespaces", "in");
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=28" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Flex_Ant_Tasks_for_Apollo"></a><h2> Flex Ant Tasks for Apollo </h2>
<p>Hi,
Can we use Flex Ant Tasks for Apollo SDK&nbsp;?
Thanks
</p>
<hr>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=29" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="How_to_Compile_multiple_.mxml"></a><h2> How to Compile multiple .mxml </h2>
<p>Thanks for the explanation ,but how to compile multiple mxml files
or take a directory of mxml or use a wild card like *.mxml while
compiling,urgent requirement please help using ant script . Is their
any way to compile the mxml fies to swf without hardcoding the names of
the mxml files in the ant script.
</p>
<hr>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=30" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Loading_flex-config_takes_ages"></a><h2> Loading flex-config takes ages </h2>
<p>I think the flex Tasks are excellent, but theres just one obstacle
for using it in the development environment for our case. The compiling
takes an extremely long time, 10-25 seconds for our application. And it
all seems because of the loading of the flex-config. </p><p>Has anyone else experienced this, or are we perhaps doing something substantially wrong in our setup?
</p>
<hr>
<p>&gt; I guess 10-25 sec is a time of SWF compilation and has nothing to do with loading of 'flex-config.xml' file
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=31" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Custom_wrapper_task_template.3F"></a><h2> Custom wrapper task template? </h2>
<p>Hi,
As far as I understand the wrapper task templates are created with
flexibility in mind, but I think its strange that we don't have a
custom template-source-dir attribute, that overrules the
template/history attributes. As an example, you might want to use
SWFObject as your detection script...
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Casper_Rasmussen&amp;action=edit" class="new" title="User:Casper Rasmussen">Casper Rasmussen</a> 04:32, 30 May 2007 (PDT)
</p><p>I would also like to see the ability to specify a template file
in this task. We have made some modifications to the template created
by Flex Builder and would like those changes to be integrated into our
nightly automated build.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php?title=User:Huych02&amp;action=edit" class="new" title="User:Huych02">huych02</a> 10:27, 12 Oct 2007 (PDT)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=32" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Minor_mod_to_html-wrapper_task_offered"></a><h2> Minor mod to html-wrapper task offered </h2>
<p>I have made a minor custom modification to the html-wrapper Ant task
to allow you to specify a filename. If not specified, it will default
to the current value of index.html. It allows you to declare in your
Ant target a different html filename if you wish. I'd be happy to send
the source for this minor modification if it would be of value to be
incorporated into the next version.
</p><p><a href="http://labs.adobe.com/wiki/index.php/User:JeffBNimble" title="User:JeffBNimble">JeffBNimble</a> 09:44, 29 Aug 2007 (CDT)
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=33" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Adding_to_default_loaded_flex-config.xml"></a><h2> Adding to default loaded flex-config.xml </h2>
<p>From the command line you can override the default loaded
flex-config.xml or you can add to it by specifying: mxmlc
-load-config+=configuration.xml SampleApplication.mxml. From the ANT
task documentation some ant mxmlc compiler options can have an
"append=true" attribute, that will add to existing values. Is this
possible for flex-config.xml values? We want to load an external config
file with only the following additions to the flex-config defaults:
</p>
<pre>     &lt;source-path&gt;
        &lt;path-element&gt;/yyy&lt;/path-element&gt;
        &lt;path-element&gt;/xxx/xxx&lt;/path-element&gt;
     &lt;/source-path&gt;
</pre>
<pre>     &lt;include-libraries&gt;
        &lt;library&gt;/libs/xxx.swc&lt;/library&gt;
     &lt;/include-libraries&gt;
</pre>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=34" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Flex_3_support.3F.3F"></a><h2> Flex 3 support?? </h2>
<dl><dd>
</dd></dl>
<p>&lt;mxmlc file="as3/granite.mxml"
</p>
<pre>           output="build/granite.swf"
           use-network="false"
           services="war/WEB-INF/flex/services-config.xml"
           keep-generated-actionscript="false"
           context-root="${WEBAPP_CONTEXT_ROOT}"&gt;
           
           &lt;load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/&gt;
           
           &lt;source-path path-element="${FLEX_HOME}/frameworks"/&gt;
           &lt;source-path path-element="as3"/&gt;            
       &lt;/mxmlc&gt;
</pre>
<p>works fine using flex2 but with flex3 beta I get this error:
</p><p>[mxmlc] command line: Error: unknown configuration variable 'load-config /Users/novotny/flex3beta/frameworks/flex-config.xml'
</p>
<pre>   [mxmlc] 
   [mxmlc] Use 'mxmlc -help' for information about using the command line.
</pre>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=35" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Try_the_flexTasks.jar_that_ships_with_the_v3_sdk"></a><h3> Try the flexTasks.jar that ships with the v3 sdk </h3>
<p>I had this same problem and found a solution here:
<a href="http://livedocs.adobe.com/labs/flex3/html/help.html?content=anttasks_1.html" class="external" rel="nofollow" target="_blank">http://livedocs.adobe.com/labs/flex3/html/help.html?content=anttasks_1.html</a>
</p><p>Click on the section called Installation under Topics at the bottom.
</p><p>Basically, use the flexTasks.jar that is in
FLEX+HOME/sdks/3.0.0/ant/lib instead of the one linked on labs. When I
put that into my ANT_HOME/lib directory that error went away. Now for
the other errors....
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=36" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Ant_Build_Errors_Integrated_into_Eclipse"></a><h2> Ant Build Errors Integrated into Eclipse </h2>
<p>Is there anyway to use the Ant Tasks and cause the output of the
build to be treated as build errors that could be linked directly to
source files included in the project being built? Suppose you do a
build and see the following in the Eclipse Console window:
</p><p>Buildfile: C:\testProj\build\build.xml
compile:
</p>
<pre>   [mxmlc] Loading configuration file C:\flex\flex2sdk\frameworks\flex-config.xml
   [mxmlc] C:\testProj\src\services\CompWrapper.as(21): col: 11 Error: Incorrect number of arguments.  Expected no more than 0.
   [mxmlc] 			super("foo"); 
   [mxmlc] 			       ^
</pre>
<p>BUILD FAILED
C:\testProj\build\build.xml:9: mxmlc - Failed with return code: 1
</p><p>Total time: 4 seconds
</p><p>The file/line reference to build.xml:9 is clickable, but the
file/line reference to CompWrapper.as(21) is not. Would this require a
full-fledged eclipse plug-in to do this or is there some other approach
to making this error integrated into the project.
</p><p><br>
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=37" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Attributes_for_runtime-shared-library-path"></a><h2> Attributes for runtime-shared-library-path </h2>
<p>How do I specify the rsl-url attribute for runtime-shared-library-path?  When I try:
</p><p>&lt;runtime-shared-library-path
path-element="${FLEX_HOME}/frameworks/libs/framework.swc"
rsl-url="/bin/framework_${FLEX_BUILD}.swz" /&gt;
</p><p>I get the error:
</p><p><i>The &lt;rutime-shared-library-path&gt; type doesn't support the "rsl-url" attribute.</i>
</p><p>However, if I remove the rsl-url attribute I get the error:
</p><p><i>Error: configuration variable 'runtime-shared-library-path' requires a value for 'rsl-url'</i>
</p><p><br>
Is my syntax incorrect?  Or is this attribute called something else?
</p><p><a href="http://labs.adobe.com/wiki/index.php?title=User:Ryan_Junee&amp;action=edit" class="new" title="User:Ryan Junee">Ryan Junee</a> 00:38, 4 Jan 2008 (PST)
</p>
<dl><dd>I actually had to read the source to figure this out. 
</dd><dd>&lt;runtime-shared-library-path path-element="${FLEX_HOME}/frameworks/libs/framework.swc"&gt;
</dd><dd>&nbsp;&nbsp;&lt;url rsl-url="/bin/framework_${FLEX_BUILD}.swz"/&gt;
</dd><dd>&lt;/runtime-shared-library-path&gt;
</dd><dd>--<a href="http://labs.adobe.com/wiki/index.php?title=User:Leedm777&amp;action=edit" class="new" title="User:Leedm777">leedm777</a> 21:08, 27 Apr 2008 (PDT)
</dd></dl>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=38" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="Problem_with_compc_task_on_linux_.28.27unknown_configuration_variable_compiler.source-path.27.29"></a><h2> Problem with compc task on linux ('unknown configuration variable compiler.source-path') </h2>
<p>Hi, we're using CruiseControl on linux to build our various
projects, including a library project. The compc task fails on linux
(but works on windows) with the error:
</p>
<pre>compile:
    [compc] Adobe Compc (Flex Component Compiler)
    [compc] Version 3.0 build 189825
    [compc] Copyright (c) 2004-2006 Adobe Systems, Inc. All rights reserved.
    [compc]
    [compc] command line: Error: unknown configuration variable 'compiler.source-path .'
    [compc]
    [compc] Use 'compc -help' for information about using the command line.
</pre>
<p>I fixed this by changing the compc script as follows:
</p>
<pre>java $VMARGS -jar "$FLEX_HOME/lib/compc.jar" +flexlib="$FLEX_HOME/frameworks" "$@"</pre>
<p>to:
</p>
<pre>java $VMARGS -jar "$FLEX_HOME/lib/compc.jar" +flexlib="$FLEX_HOME/frameworks" $@</pre>
<p>i.e. removing the quotes from the variable arguments passed to Java.  
</p><p>This probably isn't the best way to get this working, but couldn't see another way to fix it.
</p><p>Thanks.
</p><p>--<a href="http://labs.adobe.com/wiki/index.php/User:Brindy666" title="User:Brindy666">brindy666</a> 01:30, 21 Jan 2008 (PST)
</p><p>YOU ROCK....This same problem exists in the mxmlc file on linux
TOO Remove the quotes from the "$@" and everything works great!!!!!
THANKS!!!!
</p><p>--<a href="http://labs.adobe.com/wiki/index.php/User:Rick_Winscot" title="User:Rick Winscot">User:Rick Winscot</a> 02:19, 8 Aug 2008 (EST)
</p><p>If the path to your workspace and/or project folders contain
spaces... removing those quotes will prevent the compiler from finding
its targets.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=39" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="dynamically_adding_assets_to_compc"></a><h2> dynamically adding assets to compc </h2>
<p><i>Question:</i> How do I dynamically add my assets to a 'compc'
task...do I really need to add an &lt;include-file&gt; tag for each of
my assets? My list of assets is large and changes options. This needs
to be dynamic. Can I pass in a fileset somehow?
</p><p><i>Response:</i> I have written an Ant Task that will create a
config file that lists the include-file tags for each of your assets.
Email me at scott <b>[dot]</b> splavec <b>[at]</b> gmail <b>[dot]</b> com for further information.
--<a href="http://labs.adobe.com/wiki/index.php?title=User:Scott.Splavec&amp;action=edit" class="new" title="User:Scott.Splavec">Scott.Splavec</a> 06:49, 3 Apr 2008 (PDT)
</p><p><br>
<i>Response:</i> Here's how we do it:
</p>
<pre>&lt;pathconvert property="flex.classes" pathsep=" "&gt;

	&lt;fileset dir="${basedir}"&gt;
		&lt;include name="**/*.as"/&gt;
		&lt;include name="**/*.mxml"/&gt;
	&lt;/fileset&gt;

	&lt;compositemapper&gt;
		&lt;packagemapper from="${basedir}\*.as" to="*"/&gt;
		&lt;packagemapper from="${basedir}\*.mxml" to="*"/&gt;
		&lt;packagemapper from="${basedir}/*.as" to="*"/&gt;
		&lt;packagemapper from="${basedir}/*.mxml" to="*"/&gt;
	&lt;/compositemapper&gt;
			
&lt;/pathconvert&gt;

&lt;echo&gt;ActionScript classes: [${flex.classes}]&lt;/echo&gt;
		
&lt;compc output="bin/Your.swc" include-classes="${flex.classes}"&gt;
	&lt;source-path path-element="."/&gt;
&lt;/compc&gt;
</pre>
<p>As you can see, we only include .as and .mxml files.  Embeds get picked up automatically. 
</p><p>Cheers,
--<a href="http://labs.adobe.com/wiki/index.php/User:Brindy666" title="User:Brindy666">brindy666</a> 07:55, 2 Jun 2008 (PDT)
</p><p>Using  handledirsep="true" for packagemapper saves a few lines
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=40" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="flex-config.xml_error"></a><h2> flex-config.xml error </h2>
<p>I'm using Flex3.0.1.1092 and after putting flexTasks.jar in my classpath and trying the mxmlc task I get:
</p><p>Loading configuration file
/Users/novotny/flex3beta/frameworks/flex-config.xml
Error: class org.apache.xerces.util.XMLAttributesMMImpl$AttributeMMImpl
cannot access its superclass
org.apache.xerces.util.XMLAttributesImpl$Attribute
</p><p>java.lang.IllegalAccessError: class
org.apache.xerces.util.XMLAttributesMMImpl$AttributeMMImpl cannot
access its superclass
org.apache.xerces.util.XMLAttributesImpl$Attribute at
java.lang.ClassLoader.defineClass1(Native Method) at
java.lang.ClassLoader.defineClass(ClassLoader.java:675)
</p><p>--<a href="http://labs.adobe.com/wiki/index.php/User:Pwhite" title="User:Pwhite">pwhite</a> 15:23, 12 Aug 2008 (PDT)
<b>COMMENT:</b> I get the same error when calling the flex ant tasks
from Maven 1.1 but not when called directly from ant. I've even tried
replacing the xerces JARs in my Maven installation with those from my
Ant installation but I still get the same error.
</p>
<div class="editsection" style="float: right; margin-left: 5px;">[<a href="http://labs.adobe.com/wiki/index.php?title=Talk:Flex_Ant_Tasks&amp;action=edit&amp;section=41" title="Talk:Flex Ant Tasks">edit</a>]</div><a name="compc_compiling_assets_from_custom_task"></a><h2> compc compiling assets from custom task </h2>
<p>Hello,
</p><p>I have a custom task to compile a large set of assets into swc components.
My assets are stored as File in a vector, so I want to loop over the vector, add the include-file element, and compile.
</p><p>I have no clue how to make that. At the moment my code looks like this:
</p><p>for(int i=0; i&lt;vPages.size(); i++){
//each page will require a compilation task 
			CompcTask compc = new CompcTask();
			// Setting output
			compc.setDynamicAttribute("output", project.getProperty("bin.assets")+i+SWC_EXTENSION);
			Vector page = vPages.elementAt(i);
			System.out.println("processing page:"+i);
			for(int j=0; j&lt;page.size(); j++){
				File asset = (File)page.elementAt(j);
				System.out.println("asset is:"+asset.getAbsoluteFile());
				NestedAttributeElement de = (NestedAttributeElement) compc.createDynamicElement("if");
				de.setDynamicAttribute("name", asset.getName());
				de.setDynamicAttribute("path", asset.getAbsolutePath());
</p><p>			}
			//compc.execute();
		}
</p><p>I cant get the include-file to work, no clue how to pass the name and path, and so on...
I´m really hitting my head on the keyboard...
Please give me some clues...
</p>
<!-- Saved in parser cache with key labswiki:pcache:idhash:1541-1!1!0!1!0!1!0!!en and timestamp 20090521132016 -->
<div class="printfooter">
Retrieved from "<a href="http://labs.adobe.com/wiki/index.php/Talk:Flex_Ant_Tasks">http://labs.adobe.com/wiki/index.php/Talk:Flex_Ant_Tasks</a>"</div>
    <!-- end content -->
  <br class="clear-both">

</div>
<div id="footer">
  <div id="copyright-terms">
    <p><a href="http://www.adobe.com/go/labs_footer_home">Home</a> | <a href="http://www.adobe.com/go/labs_footer_technologies">Technologies</a> | <a href="http://www.adobe.com/go/labs_footer_wiki">Wikis</a> | <a href="http://www.adobe.com/go/labs_footer_download">Download</a> | <a href="http://www.adobe.com/go/labs_footer_community">Community</a> | <a href="http://www.adobe.com/go/labs_footer_rss">RSS Feeds</a> | <a href="http://www.adobe.com/go/labs_footer_search">Search</a> | <a href="http://www.adobe.com/go/labs_footer_about">About Adobe Labs</a> | <a href="http://labs.adobe.com/wiki/index.php/Macromedia_Labs:General_disclaimer" title="Adobe Labs:General disclaimer">Disclaimers</a><br>

      <a href="http://www.adobe.com/go/labs_footer_mmhome">Adobe.com Home</a> | <a href="http://www.adobe.com/go/labs_footer_support">Support</a> | <a href="http://www.adobe.com/go/labs_footer_devcenter">Developer Centers</a></p>
    <p>
       This page was last modified 17:45, 25 Feb 2009.    </p>
    <p>Copyright © 2009 Adobe Systems Incorporated. <a href="http://www.adobe.com/misc/copyright.html">All rights reserved</a>.<br>Your
use of the Adobe Labs including the download of software, submission of
comments, ideas, feature requests and techniques, and Adobe's rights to
use such submitted materials, is governed by the <a href="http://www.adobe.com/go/labs_term_of_use">Adobe Labs Terms of Use</a> and the <a href="http://www.adobe.com/go/labs_privacy_policy">Adobe Privacy Policy</a>.</p>

    <!--Creative Commons License-->
    <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank" rel="license"><img src="Talk%20Flex_Ant_Tasks_files/somerights20.png" alt="Creative
Commons License" name="ccl" id="ccl" border="0"></a>
    <p id="ccl-info">The content on this wiki is licensed under a <a href="http://creativecommons.org/licenses/by/3.0/legalcode" target="_blank" rel="license">Creative Commons
      Attribution 3.0 License</a>.  Adobe requires no attribution (<a href="http://labs.adobe.com/wiki/index.php/License">details</a>).
      <!--/Creative Commons License-->

      <!-- <rdf:RDF
xmlns="http://web.resource.org/cc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <Work rdf:about="">
            <license
rdf:resource="http://creativecommons.org/licenses/by/2.5/" />
        </Work>
        <License
rdf:about="http://creativecommons.org/licenses/by/2.5/"><permits
rdf:resource="http://web.resource.org/cc/Reproduction"/><permits
rdf:resource="http://web.resource.org/cc/Distribution"/><requires
rdf:resource="http://web.resource.org/cc/Notice"/><requires
rdf:resource="http://web.resource.org/cc/Attribution"/><permits
rdf:resource="http://web.resource.org/cc/DerivativeWorks"/></License></r
df:RDF> -->
    </p>
  </div>
  <div style="display: none;"><!-- SiteCatalyst code version: F.3. $Revision: 1.10 $ Copyright 2002 Omniture, Inc. More info available at http://www.omniture.com --><script language="JavaScript" type="text/javascript"><!--
var s_code=' '//--></script>
<script language="JavaScript" src="Talk%20Flex_Ant_Tasks_files/omniture_s_code.js" type="text/javascript"></script>
<script language="JavaScript" type="text/javascript"><!--
var s_accountName="mxmacromedia";
var s_wd=window,s_tm=new Date;if(s_code!=' '){s_code=s_dc(
s_accountName);if(s_code)document.write(s_code)}else
document.write('<im'+'g src="http://192.168.112.2O7.net/b/ss/'+s_accountName+'/1/F.3-fb/s'+s_tm.getTime()+'?[AQB]'
+'&pageName='+escape(s_wd.s_pageName?s_wd.s_pageName:(s_wd.pageName?s_wd.pageName:''))
+'&server='+escape(s_wd.s_server?s_wd.s_server:(s_wd.server?s_wd.server:''))
+'&ch='+escape(s_wd.s_channel?s_wd.s_channel:(s_wd.channel?s_wd.channel:''))
+'&[AQE]" height="1" width="1" border="0" alt="" />')
function sendAnalyticsEvent(str){var ns=s_accountName;if(str!=null)ns+=","+str;void(s_gs(ns));}
//--></script><noscript><img src="http://192.168.112.2O7.net/b/ss/mxmacromedia/1/F.3-XELvs" height="1" width="1" border="0" alt="" /></noscript><!--/DO NOT REMOVE/-->
  <!-- End SiteCatalyst code version: F.3. -->
  </div>
  <br class="clear-both">
</div>
<!-- Served by p01weblab01 in 0.04 secs. -->
</body></html>